Repository navigation
release: 0.129.0 - #215
release: 0.129.0#215tnsardesai merged 2 commits into
Conversation
Stainless-Generated-From: 72a69683e100b38933d70908470d62ab3e741f03
tnsardesai
left a comment
There was a problem hiding this comment.
Release 0.129.0: renames the browser location source metro to default (kernel/kernel#4926), plus the pending vault item and viewport changes. Checks pass.
|
🤖 Release is at https://github.com/kernel/kernel-node-sdk/releases/tag/v0.129.0 🌻 |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7c3ac94. Configure here.
| * explicitly on the session; `default` comes from the browser's region. | ||
| */ | ||
| export type BrowserLocationSource = 'override' | 'metro'; | ||
| export type BrowserLocationSource = 'override' | 'default'; |
There was a problem hiding this comment.
Location source enum value renamed
Medium Severity
BrowserLocationSource replaces metro with default on locale_source and timezone_source. Callers typed against the v0.128 metro provenance no longer typecheck, and runtime equality checks miss region-derived location. The changelog does not mention this swap.
Additional Locations (1)
Triggered by learned rule: v0.128 location, allowlist revision, AgentCard import
Reviewed by Cursor Bugbot for commit 7c3ac94. Configure here.


Automated Release PR
0.129.0 (2026-10-21)
Features
This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions
Note
Medium Risk
Renaming
BrowserLocationSourcefrommetrotodefaultcan break runtime checks on API responses; vaultcapture_tokenadds sensitive handling requirements for integrators.Overview
Release 0.129.0 bumps package and changelog metadata and refreshes generated API types to match the Kernel API.
Browser location responses now use
defaultinstead ofmetroinBrowserLocationSource(locale_source/timezone_source), with docs updated accordingly—callers that branch on'metro'need to handle'default'.Viewport docs clarify that omitted
refresh_ratedefaults to 60 Hz for GPU browsers and is otherwise inferred from width and height.Vault card enrollment actions can include an optional
capture_tokenfor Kernel-wallet embedded capture with@onkernel/vault-react(not AgentCard); treat it as sensitive like the enrollment URL.Reviewed by Cursor Bugbot for commit 7c3ac94. Bugbot is set up for automated code reviews on this repo. Configure here.